Systems and methods for checking a user into a location using a packet sequence including location information

ABSTRACT

Systems and methods are disclosed which may allow a user having a mobile device to check in to a location using a packet sequence that includes information for identifying the location. The location may be transmitted by one or more Bluetooth® Low Energy (BLE) beacons at or near the location. The user may be able to store packet sequences for various locations that may allow the user to automatically check into these locations using the store packet sequences.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/791,221, filed Oct. 23, 2017, which is a continuation of U.S. patentapplication Ser. No. 15/166,168, filed May 26, 2016, issued as U.S. Pat.No. 9,799,053, which is a continuation of U.S. patent application Ser.No. 14/039,154, filed Sep. 27, 2013, issued as U.S. Pat. No. 9,356,819,the contents of which are incorporated herein by reference.

BACKGROUND

Technical Field

Embodiments disclosed herein are related to systems and methods forchecking a user into a location using a specific sequence of packetsthat may include information identifying the location.

Related Art

Due to the increase in use of mobile devices and the improved networkingand online capabilities of these mobile devices, merchants havingphysical “brick and mortar” storefronts may also have mechanisms fordelivering advertisements and other information to the mobile deviceswhile a user of the mobile device is in the merchant store. Somemerchants may take advantage of platforms and services that allow a userto check in to the merchant or other location that they are in todeliver advertisements, specials, and other information. This allows themerchant to know that the user is at the store and provide specials andother information to the user. If the user is checking in via a socialnetwork, the user may also provide feedback about the merchant which maybe useful or helpful for the merchant. If the user is checking in via apayment processing service, such as provided by PayPal, Inc. or SanJose, Calif., the user may be provided with options for selecting,ordering, and paying for items through the payment processing servicewhen checking in, providing convenience for both the user and themerchant. In theory, checking provides benefits for both the user andthe merchant. However, the users may have to perform the tedious processof checking in every time that they visit the merchant. And, if the userdoes not check in on every visit, then neither the user nor the merchantare fully benefits from checking in.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram of a networked system, consistent with someembodiments.

FIG. 2 is a diagram illustrating a computing system, consistent withsome embodiments.

FIG. 3 is a diagram illustrating a beacon, consistent with someembodiments.

FIG. 4 is a diagram illustrating a flow of checking a user into alocation using a specific sequence of packets, consistent with someembodiments.

FIG. 5 is a diagram illustrating a flow of checking a user into alocation using a specific sequence of packets, consistent with someembodiments.

FIG. 6 is a diagram illustrating a flow of automatically checking a userinto a location using a specific sequence of packets, consistent withsome embodiments.

FIG. 7 is a flowchart illustrating a process for checking in to alocation using a specific sequence of packets, consistent with someembodiments.

FIG. 8 is a flowchart illustrating a process for checking user in to alocation using a specific sequence of packets, consistent with someembodiments.

FIG. 9 is a flowchart illustrating a process for automatically checkinguser in to a location using a specific sequence of packets, consistentwith some embodiments.

In the drawings, elements having the same designation have the same orsimilar functions.

DETAILED DESCRIPTION

In the following description specific details are set forth describingcertain embodiments. It will be apparent, however, to one skilled in theart that the disclosed embodiments may be practiced without some or allof these specific details. The specific embodiments presented are meantto be illustrative, but not limiting. One skilled in the art may realizeother material that, although not specifically described herein, iswithin the scope and spirit of this disclosure.

There is a need for providing systems and methods for checking a user inwhen the user is visiting the merchant's physical storefront.

Consistent with some embodiments, there is provided a system. The systemincludes a wireless transceiver configured to receive a packet sequencesent according to a Bluetooth® low energy (BLE) protocol, the packetsequence including information identifying a location. The system alsoincludes a network interface component configured to send a check inrequest including the received packet sequence. The system furtherincludes one or more processors configured to generate the check inrequest, and a memory configured to store the received packet sequence.

Consistent with some embodiments, there is further provided a methodincluding receiving a packet sequence sent according to a Bluetooth® lowenergy (BLE) protocol, the packet sequence including informationidentifying a location, sending a check in request to check in to thelocation when the received packet sequence matches a stored packetsequence specific to the location, receiving the packet sequencespecific to the location when the received packet sequence does notmatch a stored packet sequence specific to the location, the receivedpacket sequence specific to the location being received over a network,and storing the received packet sequence specific to the location. Themethod may also be embodied in computer-readable media.

Embodiments consistent with this disclosure may allow a merchant to uselow power transmitting devices to transmit a timed sequence that may beused to automatically check a user into a merchant or other location.These and other embodiments will be described in further detail belowwith respect to the following figures.

FIG. 1 is a block diagram of a networked system 100, consistent withsome embodiments. System 100 includes a client computing device 102 anda remote server 104 in communication over a network 106. Remote server104 may be a payment service provider server that may be maintained by apayment provider, such as PayPal, Inc. of San Jose, Calif. Remote server104 may be maintained by other service providers in differentembodiments. Remote server 104 may also be maintained by an entity withwhich sensitive credentials and information may be exchanged with clientcomputing device 102. Remote server 104 may be more generally a website, an online content manager, a service provider, such as a bank, orother entity who provides content to a user requiring userauthentication or login.

Network 106, in one embodiment, may be implemented as a single networkor a combination of multiple networks. For example, in variousembodiments, network 106 may include the Internet and/or one or moreintranets, landline networks, wireless networks, and/or otherappropriate types of communication networks. In another example, thenetwork may comprise a wireless telecommunications network (e.g.,cellular phone network) adapted to communicate with other communicationnetworks, such as the Internet.

Client computing device 102, in one embodiment, may be implemented usingany appropriate combination of hardware and/or software configured forwired and/or wireless communication over network 106. For example,client computing device 102 may be implemented as a wireless telephone(e.g., smart phone), tablet, personal digital assistant (PDA), notebookcomputer, personal computer, a connected set-top box (STB) such asprovided by cable or satellite content providers, or a video game systemconsole, a head-mounted display (HMD) or other wearable computingdevice, including a wearable computing device having an eyeglassprojection screen, and/or various other generally known types ofcomputing devices.

As shown in FIG. 1, system 100 may include one or more beacons 108 thatmay be in communication with network 106. In some embodiments, beacons108 may be installed at a merchant location, such as a brick and mortaror physical storefront of the merchant. In some embodiments, beacons 108may be Bluetooth™ Low Energy (BLE) beacons. BLE is a technology thattransmits information at a frequency of about 2.4 GHz (about 2042-2480MHz) over forty (40) 2-MHz wide channels, and has a range of about 50meter or about 160 feet. Information transmitted according to the BLEprotocol may be transmitted at a rate of about 1 Mbit/s with anapplication throughput of about 0.27 Mbit/s. In some embodiments, BLEcommunications may be secured using 128-bit Advanced Encryption Standard(AES) encryption with counter mode with a cipher block chaining messageauthentication code (CBC-MAC) and user defined security. Further, insome embodiments, BLE communications may utilize adaptive frequencyhopping, lazy acknowledgement, a 24-bit cyclic redundancy check (CRC)and 32-bit message integrity check for robustness. Moreover, in someembodiments, BLE-capable devices may consume a fraction of the power ofstandard Bluetooth® devices due to the protocol allowing low dutycycles, and being designed for applications that may not requirecontinuous data transfer. Beacons 108 may transmit one or more sequencesof information such that when a device such as client computing device102 capable of receiving information from beacons 108 comes within therange of a beacon 108, the device may receive a transmission from abeacon 108 and be instructed to perform an action, such as display anadvertisement or check in to a location or merchant using one or moreplatforms or services capable of receiving and processing check ins. Asused herein, location may refer to a merchant physical storefront,including restaurants, department stores, home improvement stores,cafés, and the like, and may also refer to a place, landmark, or museum,and generally any location to which user 110 may check in to for thepurposes of identifying themselves as being at the location andreceiving any information, specials, offers, promotions, paymentoptions, and other features associated with the location that areaccessible once user 110 has checked-in. In some embodiments, a locationmay be any place where beacon 108 may be used to automatically checkuser 110 in to the location.

Client computing device 102 may include any appropriate combination ofhardware and/or software having one or more processors and capable ofreading instructions stored on a tangible non-transitorymachine-readable medium for execution by the one or more processors.Consistent with some embodiments, client computing device 102 includes amachine-readable medium, such as a memory (not shown) that includesinstructions for execution by one or more processors (not shown) forcausing client computing device 102 to perform specific tasks. In someembodiments, the instructions may be executed by the one or moreprocessors in response to interaction by user 110. For example, suchinstructions may include browser application 112 such as a mobilebrowser application, which may be used to provide a user interface topermit user 110 to browse information available over network 106,including information hosted by remote server 104. For example, browserapplication 112 may be implemented as a web browser to view informationavailable over network 106. Browser application 112 may include agraphical user interface (GUI) that is configured to allow user 110 tointerface and communicate with remote server 104 or other serversmanaged by content providers or merchants via network 106. For example,user 110 may be able to access websites to find and purchase items, aswell as access user account information or web content.

Client computing device 102 may also include a check in application 114that may allow user 110 to check in to a location using a check inplatform or service such as may be provided by PayPal, Inc. of San Jose,Calif., Foursquare of New York, N.Y., Facebook, Inc., of Menlo Park,Calif., or Google+ of Google, Inc. of Mountain View, Calif., andimplemented by remote server 104. In some embodiments, check inapplication may include multiple application programming interfaces(APIs) for checking in to one or more of the check in platforms orservices.

In some embodiments, checking in to a location while visiting a locationsuch as a merchant physical storefront may provide user with exclusivedeals, offers, or may allow user to purchase and pay for items. In someembodiments, user 110 may check in to a location, such as a merchantlocation to access additional information about the location ormerchant. For example, upon checking in, user 110 may be able to viewand review product information about products that are offered at thelocation. As another example, user 110 may be able to see an inventoryof products that are currently in stock at the location upon checkingin. In such embodiments, the product inventory may be provided by Miloof San Jose, Calif. Checking in may provide user 110 with additionalsocial options. For example, user 110 may be presented with a list ofother users, colleagues, acquaintances, contacts, and the like that arealso checked in to the location or a nearby location. In someembodiments, user 110 may opt-in or opt-out of such features.

As noted previously, upon checking in, user 110 may receive information,specials, offers, promotions, payment options, and other featuresassociated with the location that are accessible once user 110 haschecked-in. In some embodiments, user 110 may be able to browse throughavailable information, specials, offers, promotions, payment options,and other features associated with the location once user 110 haschecked in, and then select those features that user 110 wants to useand/or save to client computing device 102. For example, user 110 maybrowse available offers or coupons upon checking in and then downloadthose that are of interest to user to client computing device 102 foruse while user 110 is at the location.

Client computing device 102 may include other applications 116 as may bedesired in one or more embodiments to provide additional featuresavailable to user 110, including accessing a user account with remoteserver 104. For example, applications 116 may include interfaces andcommunication protocols that allow the user to receive and transmitinformation through network 106 and to remote server 104 and otheronline sites. Applications 116 may also include security applicationsfor implementing client-side security features, programmatic clientapplications for interfacing with appropriate APIs over network 106 orvarious other types of generally known programs and/or applications.Applications 116 may include mobile applications downloaded and residenton client computing device 102 that enables user 110 to access contentthrough the applications.

Remote server 104, according to some embodiments, may be maintained by aservice that processes check ins so that a proprietor of a location,such as a merchant, or others know that user 110 is at the location.Remote server 104 may also be capable of providing access to amerchant's goods and services (collectively referred to as “items”) thatare for purchase and may provide a payment service processing for thepurchased items. Remote server 104 may include at least check inapplication 118, which may be configured to interact with clientcomputing device 102 connected to network 106 and beacon 108 connectedto network 106 to check user 102 in to a location. In some embodiments,checking client computing device 102 in to a location may allow user 110and client computing device 102, to access features, specials, offers,and the like offered by the location. In some embodiments, thesefeatures, specials, offers, and the like may be provided and processedby remote server 104 on behalf of the location.

Remote server 104 may also include an account database 120 that includesaccount information 122 for users having an account on remote server104, such as user 110. In some embodiments, check in application 118 maycheck user 110 and client computing device 102 in to a location based oninformation in account information 122 of account database 120. Accountinformation 122 may include information about user 110 that may be sentto the location or merchant when user 110 is checked in to thatlocation, based on preferences of user 110 or opting in or out of suchfeatures. For example, when user 110 checks in to a location, check inapplication 118 may retrieve information about user 110 to provide tothe location or merchant, such as a photograph or picture of user 110,an identity of user 110 stored in account information 122 and afrequency or recentness of a last check in at the location or nearbylocations. Additional information of user 110 from account information122 may also be provided to the location or merchant upon a successfulcheck in by user 110. The additional information may include preferencesand favorite items of user 110 at the location or other locations, pastpurchases made by user 110 at the location or nearby locations. Theadditional information may include known measurements or sizes worn byuser 110 if user 110 is checking in to a clothing or shoe store. In someembodiments, account information may also include some financialinformation related to user 110, such as how much user 110 has spent atsimilar locations, how much funds user 110 has in their accountassociated with remote server 104, and a creditworthiness of user 110.Further information may also be shared with the merchant or locationupon a check in. In some embodiments, user 110 may be able to determineand select what information may be shared with a merchant or locationupon a check in.

Remote server 104 may include other applications 124 and may also be incommunication with one or more external databases 126, that may provideadditional information that may be used by remote server 104. In someembodiments, databases 126 may be databases maintained by third parties,and may include third party account information of user 110.

Although discussion has been made of applications and applications onclient computing device 102 and remote server 104, the applications mayalso be, in some embodiments, modules. Module, as used herein, may referto a software module that performs a function when executed by one ormore processors or Application Specific Integrated Circuit (ASIC) orother circuit having memory and at least one processor for executinginstructions to perform a function, such as the functions described asbeing performed by the applications.

FIG. 2 is a diagram illustrating computing system 200, which maycorrespond to either of client computing device 102 or remote server104, consistent with some embodiments. Computing system 200 may be amobile device such as a smartphone, a tablet computer, a personalcomputer, laptop computer, netbook, or tablet computer, set-top box,video game console, head-mounted display (HMD) or other wearablecomputing device as would be consistent with client computing device102. Further, computing system 200 may also be a server or one serveramongst a plurality of servers, as would be consistent with remoteserver 104. As shown in FIG. 2, computing system 200 includes a networkinterface component (NIC) 202 configured for communication with anetwork such as network 108 shown in FIG. 1. Consistent with someembodiments, NIC 202 includes a wireless communication component, suchas a wireless broadband component, a wireless satellite component, orvarious other types of wireless communication components including radiofrequency (RF), microwave frequency (MWF), and/or infrared (IR)components configured for communication with network 108. Consistentwith other embodiments, NIC 202 may be configured to interface with acoaxial cable, a fiber optic cable, a digital subscriber line (DSL)modem, a public switched telephone network (PSTN) modem, an Ethernetdevice, and/or various other types of wired and/or wireless networkcommunication devices adapted for communication with network 108.

Consistent with some embodiments, computing system 200 includes a systembus 204 for interconnecting various components within computing system200 and communicating information between the various components. Suchcomponents include a processing component 206, which may be one or moreprocessors, micro-controllers, graphics processing units (GPUs) ordigital signal processors (DSPs), a system memory component 208, whichmay correspond to random access memory (RAM), an internal memorycomponent 210, which may correspond to read-only memory (ROM), and anexternal or static memory 212, which may correspond to optical,magnetic, or solid-state memories. Consistent with some embodiments,computing system 200 further includes a display component 214 fordisplaying information to a user 120 of computing system 200. Displaycomponent 214 may be a liquid crystal display (LCD) screen, an organiclight emitting diode (OLED) screen (including active matrix AMOLEDscreens), an LED screen, a plasma display, or a cathode ray tube (CRT)display. Computing system 200 may also include an input component 216,allowing for a user 120 of computing system 200 to input infoiniation tocomputing system 200. Such information could include payment informationsuch as an amount required to complete a transaction, accountinformation, authentication information such as a credential, oridentification information. An input component 216 may include, forexample, a keyboard or key pad, whether physical or virtual. Computingsystem 200 may further include a navigation control component 218,configured to allow a user to navigate along display component 214.Consistent with some embodiments, navigation control component 218 maybe a mouse, a trackball, or other such device. Moreover, if device 200includes a touch screen, display component 214, input component 216, andnavigation control 218 may be a single integrated component, such as acapacitive sensor-based touch screen.

Computing system 200 may perform specific operations by processingcomponent 206 executing one or more sequences of instructions containedin system memory component 208, internal memory component 210, and/orexternal or static memory 212. In other embodiments, hard-wiredcircuitry may be used in place of or in combination with softwareinstructions to implement the present disclosure. Logic may be encodedin a computer readable medium, which may refer to any medium thatparticipates in providing instructions to processing component 206 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media and volatile media. The medium may correspond toany of system memory 208, internal memory 210 and/or external or staticmemory 212. Consistent with some embodiments, the computer readablemedium may be tangible and non-transitory. In various implementations,non-volatile media include optical or magnetic disks and volatile mediaincludes dynamic memory. Some common forms of computer readable mediainclude, for example, floppy disk, flexible disk, hard disk, magnetictape, any other magnetic medium, CD-ROM, any other optical medium, punchcards, paper tape, any other physical medium with patterns of holes,RAM, PROM, EPROM, FLASH-EPROM, any other memory chip or cartridge,carrier wave, or any other medium from which a computer is adapted toread.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computing system 200. In various other embodiments of thepresent disclosure, a plurality of computing systems 200 coupled by acommunication link 220 to network 108 (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another. Computing system 200 may also include one or morewireless transceivers 222 that may each include an antenna that isseparable or integral and is capable of transmitting and receivinginfatuation according to one or more wireless network protocols, such asWi-Fi™, 3G, 4G, HDSPA, LTE, RF, NFC, IEEE 802.11a, b, g, n, ac, or ad,Bluetooth®, BLE, WiMAX, ZigBee®, etc. Computing system 200 may transmitand receive messages, data and one or more data packets, information andinstructions, including one or more programs (i.e., application code)through communication link 220 and network interface component 202 andwireless transceivers 222. Received program code may be executed byprocessing component 206 as received and/or stored in memory 208, 210,or 212.

FIG. 3 is a diagram illustrating a beacon 108, consistent with someembodiments. As shown in FIG. 3, beacon 108 includes a network interfacecomponent (NIC) 300 configured for communication with a network such asnetwork 106 shown in FIG. 1. Consistent with some embodiments, NIC 300includes a wireless communication component, such as a wirelessbroadband component, a wireless satellite component, or various othertypes of wireless communication components including radio frequency(RF), microwave frequency (MWF), and/or infrared (IR) componentsconfigured for communication 302 with network 106. Consistent with otherembodiments, NIC 300 may be configured to interface with a coaxialcable, a fiber optic cable, a digital subscriber line (DSL) modem, apublic switched telephone network (PSTN) modem, an Ethernet device,and/or various other types of wired and/or wireless networkcommunication devices adapted for communication with network 106.

Beacon 108 also includes a system bus 304 for interconnecting variouscomponents within beacon 108 and communicating information between thevarious components. Such components include a processing component 306,which may be one or more processors, micro-controllers, graphicsprocessing units (GPUs) or digital signal processors (DSPs), a memorycomponent 308, firmware 310 and one or more wireless transceivers 312that may each include an antenna that is separable or integral and iscapable of transmitting and receiving information according to one ormore wireless network protocols, such as Wi-Fi™, 3G, 4G, HDSPA, LTE, RF,NFC, IEEE 802.11a, b, g, n, ac, or ad, Bluetooth®, BLE, WiMAX, ZigBee®,etc. Beacon 108 may also include a power source 314. Power source 314may be any power source capable of providing sufficient current to powerthe components of beacon 108. In some embodiments, power source 318 maybe a battery, such as a watch battery or button cell.

In some embodiments, beacon 108 may be configured to transmitinformation using wireless transceivers 312 based on instructions storedin memory 308 and/or firmware 310 executed by processing component 306.The instructions may be stored in memory 308 and/or firmware 310 bydirectly writing the instructions to memory 308 and/or firmware 310 overcommunication link 302 to beacon hardware interface 300 or by wirelesslyreceiving instructions by wireless transceivers 312. In someembodiments, beacon 108 may be configured to transmit informationrelated to checking in to a merchant associated with beacon 108. In someembodiments, the transmitted information may include a packet sequencereceived from remote server 104 that identifies a particular merchant orlocation. The packet sequence may include packets having a small size,such as 32 bits, that may include information that may be used toidentify the location or merchant. In some embodiments, beacon 108 mayalso transmit instructions that when received by client computing device102 may cause check in application 114 or other applications 116 to beexecuted by processing component 206 to cause client computing device102 to perform a check in at the merchant or location associated withbeacon 108. Further, beacon 108 may transfer instructions that, whenreceived by client computing device 102 to allow user 110 to authorize apayment to be processed by remote server 104. In some embodiments,wireless transceiver 312 may correspond to a BLE transceiver configuredto transmit and receive information according to the BLE protocol. Insome embodiments, beacon 108 may be a BLE beacon or dongle such asdescribed in U.S. patent application Ser. No. 13/938,860, filed on Jul.10, 2013, the entire contents of which are hereby incorporated byreference in their entirety. Further, BLE beacon 108 may have a designsuch as shown in U.S. Design Application No. 29/455,720, filed May 23,2013, the entire contents of which are also incorporated herein byreference in their entirety.

FIG. 4 is a diagram illustrating a flow of checking a user into alocation using a specific sequence of packets, consistent with someembodiments. As shown in FIG. 4, remote server 104 may send to beacon108 a specific sequence of packets that may be unique to a locationwhere beacon 108 is installed and may be used to identify the location.In some embodiments, the specific sequence of packets may have a smallpacket size, for example 32 bits, and the packets may includeinformation that identify the location. Beacon 108 may store thesequence in memory 308 and broadcast the sequence when active. When user110 having client computing device 102 arrives at the location, enters amerchant's store, restaurant, and the like, client computing device 102may receive and observe the sequence broadcast by beacon 108. User 110may use client computing device 102 to execute a check in protocol tocheck in to the location, and send a request to check in to remoteserver 104 with the request including the received and observed packetsequence. Remote server 104 may then match the received sequence to astore sequence to determine the location and check user 110 into thematching location. In some embodiments, checking user 110 in to thelocation may allow user 110 to receive special offers and couponsrelated to the location. In some embodiments, checking user 110 in tothe location may allow user 110 to pay for a transaction using a paymentprocessing service such as may be provided by remote server 104 foritems that user 110 wants to buy in the location, or to authorize apayment for items that user 110 has already agreed to purchase beforeentering the location. Moreover, checking in to a location may alsoprovide user 110 with additional options specific to the location, suchas previously described. Furthermore, checking in to the location mayalso provide the location with information about user 110, based onpreferences of user 110.

Once remote server 104 has checked user 110 in to the location, remoteserver 104 may provide an identity of the merchant associated withbeacon 108 for user 110 to review to ensure that they are checking in tothe desired merchant or location. User 110 may then send a confirmationto remote server 104. When remote server 104 receives the confirmation,any actions associated with the check in may be completed. Such actionsmay include authorizing payments to a merchant or location, with suchpayments being processed by remote server 104. Such actions may alsoinclude receiving offers, specials, coupons, and the like for use at themerchant or location at which beacon 108 is installed or otherwiseassociated with.

In some embodiments, to reduce the number of packet sequences needed tocover each location, the packet sequences may correspond to a particulargeographic location, such as a square mile, zone improvement plan (ZIP)code, city, country, time zone, and the like. Consequently, for eachgeographic location, every location or merchant in that geographiclocation having beacon 108 that may be used to automatically check inuser 110 having client computing device 102 has a unique and specificpacket sequence. In such embodiments, a global positioning system (GPS)transceiver or other location-determining component in client computingdevice 102 could be used to determine a fine or rough location of clientcomputing device 102 (and the geographic location of the location ormerchant that user 110 is at), and this location could be sent to remoteserver 104 along with the check in request so that remote server 104identifies the location for checking in based on the packet sequence andthe geographic location. Similarly, other ways of partitioning locationsto reduce the number of packet sequences needed may be used. In someembodiments, the flow shown in FIG. 4 may be repeated for each locationhaving beacons 108 that transmit a specific and unique packet sequencesuch that client computing device 102 may check in to each locationbased on the received packet sequence.

FIG. 5 is a diagram illustrating a flow of checking a user into alocation using a specific sequence of packets, consistent with someembodiments. As shown in FIG. 4, remote server 104 may send to beacon108 a specific sequence of packets that may be unique to a locationwhere beacon 108 is installed and may be used to identify the location.In some embodiments, the specific sequence of packets may have a smallpacket size, for example 32 bits, and the packets may includeinformation that identify the location. Beacon 108 may store thesequence in memory 308 and broadcast the sequence when active. When user110 having client computing device 102 arrives at the location, enters amerchant's store, restaurant, and the like, client computing device 102may receive and observe the sequence broadcast by beacon 108. User 110may then be prompted to check in. When user 110 responds to the check inprompt, client computing device 102 may send a request to check in toremote server 104 with the request including the received and observedpacket sequence. Remote server 104 may then match the received sequenceto a store sequence to determine the location and check user 110 intothe matching location. In some embodiments, checking user 110 in to thelocation may allow user 110 to receive special offers and couponsrelated to the location. In some embodiments, checking user 110 in tothe location may allow user 110 to pay for a transaction using a paymentprocessing service such as may be provided by remote server 104 foritems that user 110 wants to buy in the location, or to authorize apayment for items that user 110 has already agreed to purchase beforeentering the location, or to provide additional location-specificfeatures as well as provide the location with information about user110.

Once remote server 104 has checked user 110 in to the location, remoteserver 104 may provide an identity of the merchant associated withbeacon 108 for user 110 to review to ensure that they are checking in tothe desired merchant or location. User 110 may then send a confirmationto remote server 104. When remote server 104 receives the confirmation,any actions associated with the check in may be completed. Such actionsmay include authorizing payments to a merchant or location, with suchpayments being processed by remote server 104. Such actions may alsoinclude receiving offers, specials, coupons, and the like for use at themerchant or location at which beacon 108 is installed or otherwiseassociated with. In some embodiments, the flow shown in FIG. 5 may berepeated for each location having beacons 108 that transmit a specificand unique packet sequence such that client computing device 102 may beprompted to check in to a location in each location based on thereceived packet sequence.

FIG. 6 is a diagram illustrating a flow of automatically checking a userinto a location using a specific sequence of packets, consistent withsome embodiments. As shown in FIG. 6, remote server 104 may send tobeacon 108 a specific sequence of packets that may be unique to alocation where beacon 108 is installed and may be used to identify thelocation. In some embodiments, the specific sequence of packets may havea small packet size, for example 32 bits, and the packets may includeinformation that identify the location. Beacon 108 may store thesequence in memory 308 and broadcast the sequence when active. When user110 having client computing device 102 arrives at the location, enters amerchant's store, restaurant, and the like, client computing device 102may receive and observe the sequence broadcast by beacon 108. User 110may use client computing device 102 to execute a check in protocol tocheck in to the location, and send a request to check in to remoteserver 104 with the request including the received and observed packetsequence. Remote server 104 may then match the received sequence to astore sequence to determine the location and check user 110 into thematching location. In some embodiments, checking user 110 in to thelocation may allow user 110 to receive special offers and couponsrelated to the location. In some embodiments, checking user 110 in tothe location may allow user 110 to pay for a transaction using a paymentprocessing service such as may be provided by remote server 104 foritems that user 110 wants to buy in the location, or to authorize apayment for items that user 110 has already agreed to purchase beforeentering the location. Moreover, checking in to a location may alsoprovide user 110 with additional options specific to the location, suchas previously described. Furthermore, checking in to the location mayalso provide the location with information about user 110, based onpreferences of user 110.

Once remote server 104 has checked user 110 in to the location, remoteserver 104 may provide an identity of the merchant associated withbeacon 108 for user 110 to review to ensure that they are checking in tothe desired merchant or location. User 110 may then send a confirmationto remote server 104. When remote server 104 receives the confirmation,any actions associated with the check in may be completed. Such actionsmay include authorizing payments to a merchant or location, with suchpayments being processed by remote server 104. Such actions may alsoinclude receiving offers, specials, coupons, and the like for use at themerchant or location at which beacon 108 is installed or otherwiseassociated with. Remote server 104 may then send client computing device102 a message requesting permission for automatically checking user 110in whenever user 110 is at the location. When user 110 accepts orenrolls in an automatic check in, remote server 104 may send thespecific sequence of packets that correspond to the location to clientcomputing device 102. Client computing device 102 may then store thespecific sequence of packets in any of memory 208-212. Consequently, thenext time user 110 having client computing device 102 arrives at orenters the same location, when client computing device 102 receives thespecific sequence of packets sent by beacon 108, processing component206 of client computing device 102 may match the received sequence tothe specific sequence stored in any of memories 208-212 andautomatically execute a check in protocol to send a check in request toremote server 104 when the received sequence matches the storedsequence. In some embodiments, the flow shown in FIG. 6 may be repeatedfor each location having beacons 108 that transmit a specific and uniquepacket sequence such that any of memories 208-212 of client computingdevice 102 may store a specific and unique sequence for each locationenabling user 110 having client computing device 102 to automaticallycheck in to each location based on the received packet sequence.

FIG. 7 is a flowchart illustrating a process 700 for checking in to alocation using a specific sequence of packets, consistent with someembodiments. For the purpose of illustration, FIG. 7 may be describedwith reference to any of FIGS. 1-6. Process 700 may be embodied incomputer-readable instructions for execution by one or more processorssuch that the steps of process 700 may be performed by client computingdevice 102. In some embodiments, check in application 114 of clientcomputing device 102 may include instructions for performing one or moresteps of process 700. As shown in FIG. 7, process 700 may begin whenclient computing device 102 receives a packet sequence (702). In someembodiments user 110 having client computing device 102 may arrive at alocation, enter a merchant's store, restaurant, and the like having abeacon 108, and client computing device 102 may receive a packetsequence from beacon 108. In some embodiments, the packet sequence maycomprise a sequence of packets having a small packet size which, in someembodiments, may be 32 bits, having a predetermined time therebetween,the packets including information specific to the location that may beused to identify the location. In some embodiments, the packet sequencemay include instructions that, when executed by processing component 206of client computing device 102 may cause processing component 206 toperform an action.

When processing component 206 determines that the received packetsequence matches a stored packet sequence (704), network interfacecomponent 202 of client computing device 102 may execute a check inprotocol and send a check in request (706). When processing component206 determines that the received packet sequence does not match a storedpacket sequence, client computing device 102 may execute a check inprotocol (708) and send a check in request (710). In some embodiments,the packet sequence may have instructions that may be executed byprocessing component 206 of client computing device 102 and may causeclient computing device 102 to perform an action, such as executing acheck in protocol, sending a check in request, and/or executing check inapplication 114. In some embodiments, the check in request may be sentto remote server 104. Client computing device 102 may receive anidentification of the location that they are checking in to (712),allowing user 110 to confirm or deny the check in request. When userdoes not confirm the location to which they are attempting to check in,process 700 may terminate or end (716). When user 110 confirms thelocation, client computing device 102 may send a confirmation (718) toremote server 104. Client computing device 102 may then receive anotification that an action has been completed (720). In someembodiments, the completed action may be a successful check in, and/orthe authorization of a payment, completion of a transaction, a receiptof an offer, and the like. Moreover, the completed action may beadditional location-specific features, such as previously described.

After the action has been completed, client computing device 102 mayreceive a request for permission to automatically check in at thelocation on future visits (722). When user 110 grants permission clientcomputing device 102 may send a permission grant (724). Client computingdevice 102 may then receive a packet sequence that is specific to thatlocation (726) and store the location specific packet sequence in one ofmemories 208-212 (728). Consequently, the next time user 110 visits thatlocation with client computing device 102 user may receive a packetsequence from beacon 108 (702) and automatically execute a check inprotocol and send a check in request (706). In some embodiments, beacon108 as referred to with respect to process 700 may refer to a BLEbeacon. Moreover, information sent from and received at client computingdevice 102 in process 700 may be information sent in response toinstructions executed by processing component 206 and sent from andreceived by at least one of network interface component 202 and wirelesstransceiver 222.

FIG. 8 is a flowchart illustrating a process 800 for checking user 110in to a location using a specific sequence of packets, consistent withsome embodiments. For the purpose of illustration, FIG. 8 may bedescribed with reference to any of FIGS. 1-6. Process 800 may beembodied in computer-readable instructions for execution by one or moreprocessors such that the steps of process 800 may be performed by remoteserver 104. In some embodiments, check in application 118 of remoteserver 104 may include instructions for performing one or more steps ofprocess 800. As shown in FIG. 8, process 800 may begin when remoteserver 104 receives a check in request (802). In some embodiments, thecheck in request may be received from client computing device 102 andmay be a request to check user 110 in to a particular location. In someembodiments, the check in request may include a specific sequence ofpackets that may also be received along with the check in request fromclient computing device 102 (804). In some embodiments, the packetsequence may comprise a sequence of packets having a small packet size,for example 32 bits, having a predetermined time therebetween that maybe unique to a predetermined location or used to identify a particularlocation. The packet sequence may also include information in thepackets that are specific to the location and may be used to identifythe location.

Processing component 206 of remote server 106 may attempt to match thereceived packet sequence to a particular location (806) and check user110 in to the location based on a matching packet sequence (808). Insome embodiments, particular locations may have a packet sequence thatidentifies that particular location and may be saved in account database120 and/or databases 126. Processing component 206 may attempt to matchthe received packet sequence to one of the saved locations and checkuser 110 in to the matching location. Remote server 104 may then send anidentity of the location or merchant for confirmation purposes (810).When remote server 104 does not receive a confirmation, process 800 mayend or terminate (814). When remote server 104 receives a confirmation,remote server 104 may complete an action (816). In some embodiments,completing an action may include processing a payment or authorizing apayment, checking user 110 in to the location or merchant, or sending anoffer and the like to client computing device 102. Information sent fromand received at remote server 104 in process 800 may be information sentin response to instructions executed by processing component 206 andsent from and received by at least one of network interface component202 and wireless transceiver 222.

FIG. 9 is a flowchart illustrating a process 900 for automaticallychecking user 110 in to a location using a specific sequence of packets,consistent with some embodiments. For the purpose of illustration, FIG.9 may be described with reference to any of FIGS. 1-6. Process 900 maybe embodied in computer-readable instructions for execution by one ormore processors such that the steps of process 900 may be performed byremote server 104. In some embodiments, check in application 118 ofremote server 104 may include instructions for performing one or moresteps of process 900. As shown in FIG. 9, process 900 may begin whenremote server 104 receives a check in request (902). In someembodiments, the check in request may be received from client computingdevice 102 and may be a request to check user 110 in to a particularlocation. The request may also include a specific packet sequence thatmay be unique to that particular location or otherwise may includeinformation that may be used to identify the location. Remote server 104may then determine if user 110 is enrolled in automatic check ins atthis location (904). In some embodiments, user 110 may grant permissionto be automatically checked in to one or more locations. When user 110is already enrolled in automatic check ins at the location, remoteserver 104 may proceed to match the received packet sequence to aspecific location (906) and check user 110 in at the location (908).

However, when user is not automatically enrolled in automatic check insat this location (904) remote server 104 may send a request forpermission to automatically check in at the location (910). When userdoes not grant permission (912) remote server 104 may proceed to matchthe received sequence to the particular location (906) and check user110 in at the location (908). However, when user 110 grants permissionand enrolls in automatic check ins at the location, remote server 104may send a specific packet sequence to client computing device 102(914). In some embodiments, the packet sequence may comprise a sequenceof packets having a small packet size which, in some embodiments, may be32 bits, having a predetermined time therebetween, and may includeinstructions for execution by processing component of client computingdevice 102. The packet sequence may also include information in thepackets that is specific to the location and may be used to identify thelocation. Moreover, the packet sequence may be stored by clientcomputing device 102 and may be used to automatically check in at alocation, as the packet sequence may match a packet sequence transmittedby a BLE beacon 108 at that location. Information sent from and receivedat remote server 104 in process 900 may be information sent in responseto instructions executed by processing component 206 and sent from andreceived by at least one of network interface component 202 and wirelesstransceiver 222.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more machine-readable mediums,including non-transitory machine-readable medium. It is alsocontemplated that software identified herein may be implemented usingone or more general purpose or specific purpose computers and/orcomputer systems, networked and/or otherwise. Where applicable, theordering of various steps described herein may be changed, combined intocomposite steps, and/or separated into sub-steps to provide featuresdescribed herein.

Consequently, embodiments as described herein may provide systems andmethods for automatically checking a user in to a location using apacket sequence sent by a BLE beacon that is unique to the locationand/or identifies the location. The examples provided above areexemplary only and are not intended to be limiting. One skilled in theart may readily devise other systems consistent with the disclosedembodiments which are intended to be within the scope of thisdisclosure. As such, the application is limited only by the followingclaims.

What is claimed is:
 1. A system, comprising: one or more processors, oneor more computer-readable memories, with program instructions stored onthe one or more computer-readable memories, the one or more processorsconfigured to execute the program instructions to cause the system toperform operations comprising: receiving a check-in request from a userdevice, wherein the check-in request includes a plurality of datapackets, the plurality of data packets corresponding to a firstsequence; determining one or more time intervals between consecutivepackets from the plurality of data packets of the first sequence;determining that the first sequence corresponds to a stored sequenceassociated with a location of a first merchant based on the determinedone or more time intervals; and in response to determining that thefirst sequence corresponds to the stored sequence associated with thelocation of the first merchant, performing a check-in of the user devicewith the first merchant at the location.
 2. The system of claim 1,wherein the check-in request further includes payment informationassociated with the first merchant.
 3. The system of claim 2, theoperations further comprising: in response to the performing thecheck-in of the user device, processing a payment from the user deviceto the first merchant using the payment information.
 4. The system ofclaim 1, the operations further comprising: in response to theperforming the check-in of the user device, transmitting an offerassociated with the first merchant to the user device.
 5. The system ofclaim 1, the operations further comprising: in response to theperforming the check-in of the user device, prompting a user of the userdevice to authorize a payment for a purchase of an item sold by thefirst merchant.
 6. The system of claim 1, the operations furthercomprising: in response to the performing the check-in of the userdevice, prompting a user of the user device to confirm that the check-inwas desired.
 7. The system of claim 6, the operations furthercomprising: in response to receiving, from the user device, aconfirmation that the check-in was desired, transmitting an offerassociated with the first merchant to the user device.
 8. A methodcomprising: transmitting a first sequence of packets to a merchantcommunication device, the first sequence of packets specific to a firstlocation where the merchant communication device is located; receiving acheck-in request from a user device, wherein the check-in requestincludes a plurality of data packets, the plurality of data packetscorresponding to the first sequence; determining that the first sequencecorresponds to a stored sequence associated with a second location of afirst merchant; and in response to determining that the first sequencecorresponds to the stored sequence associated with the second locationof the first merchant, performing a check-in of the user device with thefirst merchant at the second location.
 9. The method of claim 8, whereinthe check-in request further includes payment information associatedwith the first merchant.
 10. The method of claim 9, further comprising:in response to the performing the check-in of the user device,processing a payment from the user device to the first merchant usingthe payment information.
 11. The method of claim 8, further comprising:in response to the performing the check-in of the user device,transmitting an offer associated with the first merchant to the userdevice.
 12. The method of claim 8, further comprising: in response tothe performing the check-in of the user device, prompting a user of theuser device to authorize a payment for a purchase of an item sold by thefirst merchant.
 13. The method of claim 8, further comprising: inresponse to the performing the check-in of the user device, prompting auser of the user device to confirm that the check-in was desired; and inresponse to receiving, from the user device, a confirmation that thecheck-in was desired, transmitting an offer associated with the firstmerchant to the user device.
 14. A computer program product comprising:one or more computer-readable tangible storage devices, and programinstructions stored on at least one of the one or more storage devices,the program instructions when executed cause a machine to performoperations comprising: receiving a check-in request from a user device,wherein the check-in request includes a plurality of data packets, theplurality of data packets corresponding to a first sequence, whereineach of the plurality of packets has a packet size of 32 bits or fewer;determining that the first sequence corresponds to a stored sequenceassociated with a location of a first merchant; and in response todetermining that the first sequence corresponds to the stored sequenceassociated with the location of the first merchant, performing acheck-in of the user device with the first merchant at the location. 15.The computer program product of claim 14, wherein the check-in requestfurther includes payment information associated with the first merchant.16. The computer program product of claim 15, the operations furthercomprising: in response to the performing the check-in of the userdevice, processing a payment from the user device to the first merchantusing the payment information.
 17. The computer program product of claim14, the operations further comprising: in response to the performing thecheck-in of the user device, transmitting an offer associated with thefirst merchant to the user device.
 18. The computer program product ofclaim 14, the operations further comprising: in response to theperforming the check-in of the user device, prompting a user of the userdevice to authorize a payment for a purchase of an item sold by thefirst merchant.
 19. The computer program product of claim 14, theoperations further comprising: in response to the performing thecheck-in of the user device, prompting a user of the user device toconfirm that the check-in was desired.
 20. The computer program productof claim 19, the operations further comprising: in response toreceiving, from the user device, a confirmation that the check-in withthe location of the first merchant was desired, transmitting an offerassociated with the first merchant to the user device.